Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0934

reference
449-tree-1
name
0934
tree-preservation-order

undefined

449-tpo-1
uprn
address-text
point
POINT (-1.009698 50.890044)
geometry
MULTIPOLYGON (((-1.009641 50.890038,-1.009643 50.890050,-1.009651 50.890060,-1.009664 50.890068,-1.009679 50.890073,-1.009697 50.890075,-1.009715 50.890073,-1.009731 50.890068,-1.009743 50.890060,-1.009752 50.890050,-1.009755 50.890039,-1.009752 50.890028,-1.009744 50.890018,-1.009732 50.890010,-1.009716 50.890005,-1.009698 50.890003,-1.009681 50.890005,-1.009665 50.890010,-1.009652 50.890017,-1.009644 50.890027,-1.009641 50.890038)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL